Yesterday we used eseutil /p to repair our broken Exchange 2000 server. Due to a disk failure (or ?), we lost one of the needed .log files (E00nnnn.log, and we didn't have a backup). So doing a repair was our only option. After the repair, we were able to start and mount the information store, and everything looked OK, and it appears we lost very few emails. HOWEVER, one user now can't receive emails (other users appear to be working OK). It appears that all emails sent to this one user get queued waiting for local delivery. The message history of these queued messages shows the following entry repeated every 5 minutes: SMTP: Message Delivered Locally to user. But we never see the expected entry: "SMTP Store Driver: Message Delivered Locally to Store to user" We have restarted the Win2K server that's hosting Exchange several times. And we deleted the oldest entry from the queue, but nothing has helped. Any ideas what could be causing this? And how to fix it? DT

I would suggest that you do a ESEUTIL /D to defragment the DB and then also run ISINTEG to ensure the DB is clean of errors. The /P just threw away the corrupt pages so that you could mount the DB but you need to do the above commands to ensure the DB is healthy. NOTE: BACKUP THE DATABASE BEFORE YOU DO ANY OF THE ABOVE ACTIONS so THAT YOU HAVE A ROLLBACK POSITION I would migrate the users to another database ASAP since IMHO once you have to /P a DB its suspect from there on out. Once you have completed the above let me know if the issue still persist, but until you have the database in a truly healthy state its the main suspect IMHO Troy Werelius Lucid8

Troy, I did a defrag yesterday while I had the store offline, but I didn't know about ISINTEG (I'm new to Exchange "internals"). So per your recommendation, I just now ran ISINTEG without -fix against my public and private stores, but it didn't find any errors. But just on a hunch, I ran it again with -fix, and (surprise) it made some fixes. So I remounted the stores, and the problem has now gone away! Thanks for your quick (and correct) advice! BTW: the one user who was affected by this problem was the president of the company. DT

Excellent news and yeah its interesting with ISINTEG i.e. without the -fix it can report nothing at all or just warnings and yet when you do a fix it finds all sorts of interesting things to fix. Part of this is because its a cascading effect, i.e. until it gets in an really tries to align the information it cant do anything and then once it finds one issue it can uncover others to fix etc. Kind of like moving a box thats sitting in the corner not causing any issue and then when you lift it up OMG whats that? Anyway glad to hear that it was resolved and I am sure the president is happy as well eh? BTW: If you want to check out some interesting products for Exchange check out our web site www.lucid8.com Troy Werelius Lucid8